Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote - Mailing list pgsql-ports

From Herouth Maoz
Subject Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote
Date
Msg-id l03130306b39fd51af2c4@[147.233.159.109]
Whole thread Raw
In response to Re: [PORTS] Port Bug Report: parse error not detected on unterminated quote  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-ports
At 16:31 +0300 on 30/06/1999, Thomas Lockhart wrote:


> And seems to be:
>
> postgres=> select * from mytable' where id = 1234;
> postgres'> '
> postgres-> ;
> ERROR:  parser: parse error at or near "'"
> postgres=>
>
> This is on a RH5.2 system with with the cvs distribution of Postgres
> (rather than v6.5 exactly). But the parsing behavior should be the
> same. I'm not sure what could be different in our installations...

In psql, it will probably never be a problem, because it demands that you
close the quotation mark (that "postgres'>" prompt). It doesn't send
anything to the backend until you have closed the quotation and type \g or
';'.

But what happens if the above query is sent through one of the other
interfaces, like pqlib?

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma



pgsql-ports by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: [PORTS] Port Bug Report: Can't create indicies on type "timestamp"
Next
From: Thomas Lockhart
Date:
Subject: [Fwd: [PORTS] Port Bug Report: parse error not detected on unterminated quote]